Skip to content

tools,win: upgrade install additional tools to Visual Studio 2026#61562

Open
MikeMcC399 wants to merge 1 commit intonodejs:mainfrom
MikeMcC399:msvs-install-tools-vs2026-v18
Open

tools,win: upgrade install additional tools to Visual Studio 2026#61562
MikeMcC399 wants to merge 1 commit intonodejs:mainfrom
MikeMcC399:msvs-install-tools-vs2026-v18

Conversation

@MikeMcC399
Copy link
Contributor

@MikeMcC399 MikeMcC399 commented Jan 28, 2026 •
edited
Loading

Situation

Minimum versions for Visual Studio 2026 to run with node-gyp are:

These are currently given in the branches main, v25.x and expected in the next v24.x release. Branches v22.x and v20.x would be expected to remain on npm 10.x and so will not be eligible.

Branch npm Minimum versions available
main 11.8.0 YES
v25.x 11.8.0 YES
v24.x 11.6.2 NO
v24.x-staging 11.8.0 YES
v22.x 10.9.4 NO
v20.x 10.8.2 NO

Change

Update tools/msvs/install_tools/install_tools.bat from Visual Studio 2022 to 2026,

from Chocolatey package:

to

Logs

Upgraded:
 - chocolatey-compatibility.extension v1.0.0
 - chocolatey-core.extension v1.4.0
 - chocolatey-dotnetfx.extension v1.0.1
 - chocolatey-visualstudio.extension v1.13.0
 - chocolatey-windowsupdate.extension v1.0.5
 - dotnetfx v4.8.0.20220524
 - KB2919355 v1.0.20160915
 - KB2919442 v1.0.20160915
 - KB2999226 v1.0.20181019
 - KB3033929 v1.0.5
 - KB3035131 v1.0.3
 - python v3.14.2
 - python3 v3.14.2
 - python314 v3.14.2
 - vcredist140 v14.44.35211
 - vcredist2015 v14.0.24215.20170201
 - visualstudio2026buildtools v118.2.0
 - visualstudio2026-workload-vctools v1.0.0
 - visualstudio-installer v2.0.7

Size requirements

The current statement in the script is still accurate:

This will require about 7 GiB of free disk space, plus any space necessary to install Windows updates.

cc: @StefanStojanovic

@nodejs-github-bot nodejs-github-bot added install Issues and PRs related to the installers. needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. windows Issues and PRs related to the Windows platform. labels Jan 28, 2026
@MikeMcC399 MikeMcC399 marked this pull request as ready for review January 28, 2026 12:22
@richardlau richardlau added dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. labels Jan 28, 2026
@MikeMcC399
Copy link
Contributor Author

MikeMcC399 commented Jan 31, 2026 •
edited
Loading

I have now tested this end-to-end for Visual Studio 2026, building a node*.msi package, using it to install Node.js and then successfully installing an npm package that needs node-gyp.

Steps to verify

With Visual Studio Build Tools 2026 installed, add

  • "Desktop development with C++" workload
  • Individual components
    • C++ Clang Compiler for Windows
    • MSBuild support for LLVM (clang-cl) toolset
    • .NET SDK (includes .NET 10.0 Runtime (Long Term Support))

and Python 3.14.2 (current latest)

Execute .\vcbuild release msi in a PowerShell 7.5.4 terminal window in this PR branch.

Save node-v26.0.0-x64.msi

Reboot

Uninstall:

  • Visual Studio Build Tools using Visual Studio Installer
  • Visual Studio Installer
  • Python, Python Installer
  • Node.js and any Node Version Manager

Delete C:\ProgramData\chocolatey, C:\ProgramData\ChocolateyHttpCache and user / system environment variables referencing Chocolatey (may delete other unrelated packages) if present

Execute node-v26.0.0-x64.msi, select "Tools for Native Modules"

Confirm that:

  • Visual Studio Build Tools 2026 with workload "Desktop development with C++" is re-installed
  • Python 3.14 is re-installed

Uninstall Node.js 26.0.0-pre
Install node-v25.5.0-x64.msi, do not select "Tools for Native Modules"

Confirm that the following is able to install in a Git Bash terminal. This uses node-gyp and Visual Studio:

cd $(mktemp -d)
npm install cpu-features

@MikeMcC399

This comment was marked as outdated.

Sign in to view
@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. request-ci Add this label to start a Jenkins CI on a PR. labels Feb 2, 2026
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Feb 2, 2026
@nodejs-github-bot
Copy link
Collaborator

nodejs-github-bot commented Feb 2, 2026

CI: https://ci.nodejs.org/job/node-test-pull-request/71166/

@MikeMcC399
Copy link
Contributor Author

MikeMcC399 commented Feb 4, 2026 •
edited
Loading

This seems to have failed in unrelated Linux workflows. This is a Windows-related change only. Could it be given another chance in CI? Or isn't that necessary? I'm still a little unfamiliar with processes here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cjihrig cjihrig cjihrig approved these changes

@StefanStojanovic StefanStojanovic StefanStojanovic approved these changes

Assignees

No one assigned

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. install Issues and PRs related to the installers. needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. windows Issues and PRs related to the Windows platform.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@MikeMcC399 @nodejs-github-bot @cjihrig @StefanStojanovic @richardlau @aduh95